Skip to content

Conversation

@jimklimov
Copy link
Member

Closes: #3312

Using nut.exe -N for testing and pressing Ctrl+C should now cause the started daemons to be killed off. Previously they would linger and e.g. preclude subsequent experiments with the service wrapper.

Console close events are ignored, so there is a way to indefinitely keep the daemons started by test-mode wrapper running (kill via Task Manager then).

@jimklimov jimklimov added this to the 2.8.5 milestone Feb 9, 2026
@jimklimov jimklimov added enhancement Windows service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug impacts-release-2.8.4 Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks) labels Feb 9, 2026
@AppVeyorBot
Copy link

…xiting from "nut.exe -N" with Ctrl+C [networkupstools#3312]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
@jimklimov jimklimov merged commit 43a9336 into networkupstools:master Feb 10, 2026
62 of 65 checks passed
@jimklimov jimklimov deleted the issue-3312 branch February 10, 2026 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement impacts-release-2.8.4 Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks) service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug Windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test mode of nut.exe wrapper on Windows leaves daemons running after Ctrl+C

2 participants